-
Notifications
You must be signed in to change notification settings - Fork 409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use jemalloc to trace thread allocation #8844
Conversation
Co-authored-by: Lloyd-Pottiger <60744015+Lloyd-Pottiger@users.noreply.github.com>
Signed-off-by: CalvinNeo <calvinneo1995@gmail.com>
Co-authored-by: JaySon <tshent@qq.com>
dbms/src/Common/MemoryTrace.cpp
Outdated
@@ -0,0 +1,37 @@ | |||
// Copyright 2024 PingCAP, Inc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This filename is easy to confuse with MemoryTracker.cpp
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed into MemoryAllocTracker
/run-all-tests |
/unhold |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JaySon-Huang, JinheLin, Lloyd-Pottiger The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/run-all-tests |
/run-all-tests |
/run-unit-test |
What problem does this PR solve?
Issue Number: close #8835, close #8589
Problem Summary:
Basicly two modes:
We don't directly monitor at FFI boundary because:
See also https://github.com/pingcap/tidb-engine-ext/pull/366/files
What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note